fix(tools): offload blocking workspace I/O to threads#346
Open
HassanRady wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Prevent the Tau TUI/event loop from freezing and becoming unresponsive during file operations.
The Problem
Currently, the read, write, and edit tools run filesystem operations (reading bytes, reading text, writing text) synchronously on the main thread. If workspace files are large or located on slow virtual/network mounts, they block the entire asyncio event loop. This stops spinner animations, UI rendering, and renders keyboard cancellation shortcuts unresponsive.
The Solution
Offload all blocking workspace filesystem operations in src/tau_coding/tools.py to a background thread pool using asyncio.to_thread